-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fresh {}
is subtype of object
#49503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@typescript-bot test this |
Heya @ahejlsberg, I've started to run the diff-based user code test suite on this PR at 26df65a. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at 26df65a. You can monitor the build here. |
Heya @ahejlsberg, I've started to run the extended test suite on this PR at 26df65a. You can monitor the build here. |
Heya @ahejlsberg, I've started to run the abridged perf test suite on this PR at 26df65a. You can monitor the build here. Update: The results are in! |
@ahejlsberg Here they are:Comparison Report - main..49503
System
Hosts
Scenarios
Developer Information: |
@ahejlsberg |
Heya @ahejlsberg, I've run the RWC suite on this PR - assuming you're on the TS core team, you can view the resulting diff here. |
What is going on with xstate emit time? @typescript-bot perf test this |
Heya @DanielRosenwasser, I've started to run the perf test suite on this PR at 26df65a. You can monitor the build here. Update: The results are in! |
@DanielRosenwasser Here they are:Comparison Report - main..49503
System
Hosts
Scenarios
Developer Information: |
@DanielRosenwasser is a small drop (2-4%) in XState's emit time concerning here? 🤔 Or do I read those reports all wrong? |
I don't know why it's showing a drop, the emit time is identical; only the variability has shrunk if I've understood it correctly (@weswigham @rbuckton) |
It looks like total time has improved (i.e., is lower) across the board. |
There's a Stack Overflow question that seems to be related to this PR: interface Baz {
foo: { a: number };
}
const createDefaultExample = <K extends keyof Baz>(x: K): Baz[K] & { x: K; } => {
return { a: 0, x }; // okay in TS4.7, error in TS4.8
} Looks like the fix for #49520 might have broken this. Is it a bug and should this be filed as such? Or is it intended in some way? EDIT: Looks like the above was fixed by #50261 but this one persists: type Foo<K> = K extends unknown ? { a: number } : unknown
const createDefaultExample = <K,>(x: K): Foo<K> & { x: K; } => {
return { a: 1, x: x }; // okay in TS 4.7.4, error in TS 4.8.2
} Same question, I guess... bug? Not bug? New issue? |
Fixes #49480.
Fixes #49520.